| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.9.2.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.9.2 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_9_2_Support_Financial_Eligibility_Verification |
| Title | AS.9.2 Support Financial Eligibility Verification (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Support interactions with other systems, applications, and modules to enable eligibility verification for health insurance and special programs, including verification of benefits and pre-determination of coverage. |
| Purpose | Retrieves information needed to support verification of coverage at the appropriate juncture in the encounter workflow. Improves patient access to covered care and reduces claim denials. When eligibility is verified, the system could prompt a provider to capture eligibility information needed for processing administrative and financial documentation, reports or transactions; updating or flagging any inconsistent data. In addition to health insurance eligibility, this function would support verification of registration in programs and registries, such as chronic care case management and immunization registries. A system would likely verify health insurance eligibility prior to the encounter, but would verify registration in case management or immunization registries during the encounter. Example: A US Realm example could include information about capturing VFC eligibility status as this is a requirement for any provider using federally funded vaccine in the USA. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Support interactions with other systems, applications, and modules to enable eligibility verification for health insurance and special programs, including verification of benefits and pre-determination of coverage.
Retrieves information needed to support verification of coverage at the appropriate juncture in the encounter workflow. Improves patient access to covered care and reduces claim denials. When eligibility is verified, the system could prompt a provider to capture eligibility information needed for processing administrative and financial documentation, reports or transactions; updating or flagging any inconsistent data. In addition to health insurance eligibility, this function would support verification of registration in programs and registries, such as chronic care case management and immunization registries. A system would likely verify health insurance eligibility prior to the encounter, but would verify registration in case management or immunization registries during the encounter. Example: A US Realm example could include information about capturing VFC eligibility status as this is a requirement for any provider using federally funded vaccine in the USA.
| AS.9.2#01 | SHOULD |
The system SHOULD provide the ability to capture patient health plan eligibility information for date(s) of service. |
| AS.9.2#02 | conditional SHALL |
IF the system does not provide the ability to exchange electronic eligibility information (e.g., health plan coverage dates) with internal and external systems, THEN the system SHALL provide the ability to enter and maintain patient health plan coverage dates. |
| AS.9.2#03 | MAY |
The system MAY provide the ability to capture general benefit coverage information for patients. |
| AS.9.2#04 | dependent SHOULD |
The system SHOULD store eligibility date(s) of service, coverage dates, general benefits and other benefit coverage documentation for service rendered according to scope of practice, organizational policy, and/or jurisdictional law. |
| AS.9.2#05 | MAY |
The system MAY provide the ability to capture electronic eligibility information from internal and external systems. |
| AS.9.2#06 | MAY |
The system MAY provide the ability to render information received through electronic prescription eligibility checking. |
| AS.9.2#07 | MAY |
The system MAY provide the ability to capture and maintain patient registration in special programs (e.g., registries and case management). |
| AS.9.2#08 | MAY |
The system MAY provide the ability to analyze eligibility and coverage information for inconsistencies (e.g., coverage dates, patient identity data, coverage status), and render a notification to the user regarding identified inconsistencies. |
| AS.9.2#09 | MAY |
The system MAY provide the ability to render information received through provider eligibility checking. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.9.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Support interactions with other systems, applications, and modules to enable eligibility verification for health insurance and special programs, including verification of benefits and pre-determination of coverage.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Retrieves information needed to support verification of coverage at the appropriate juncture in the encounter workflow. Improves patient access to covered care and reduces claim denials. When eligibility is verified, the system could prompt a provider to capture eligibility information needed for processing administrative and financial documentation, reports or transactions; updating or flagging any inconsistent data. In addition to health insurance eligibility, this function would support verification of registration in programs and registries, such as chronic care case management and immunization registries. A system would likely verify health insurance eligibility prior to the encounter, but would verify registration in case management or immunization registries during the encounter.\nExample:\nA US Realm example could include information about capturing VFC eligibility status as this is a requirement for any provider using federally funded vaccine in the USA.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.9.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture patient health plan eligibility information for date(s) of service.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.9.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the system does not provide the ability to exchange electronic eligibility information (e.g., health plan coverage dates) with internal and external systems, THEN the system SHALL provide the ability to enter and maintain patient health plan coverage dates.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.9.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture general benefit coverage information for patients.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.9.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD store eligibility date(s) of service, coverage dates, general benefits and other benefit coverage documentation for service rendered according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.9.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture electronic eligibility information from internal and external systems.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.9.2#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render information received through electronic prescription eligibility checking.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.9.2#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture and maintain patient registration in special programs (e.g., registries and case management).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.9.2#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to analyze eligibility and coverage information for inconsistencies (e.g., coverage dates, patient identity data, coverage status), and render a notification to the user regarding identified inconsistencies.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.9.2#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render information received through provider eligibility checking.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.9.2",
"version" : "2.1.0",
"name" : "AS_9_2_Support_Financial_Eligibility_Verification",
"title" : "AS.9.2 Support Financial Eligibility Verification (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Support interactions with other systems, applications, and modules to enable eligibility verification for health insurance and special programs, including verification of benefits and pre-determination of coverage.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Retrieves information needed to support verification of coverage at the appropriate juncture in the encounter workflow. Improves patient access to covered care and reduces claim denials. When eligibility is verified, the system could prompt a provider to capture eligibility information needed for processing administrative and financial documentation, reports or transactions; updating or flagging any inconsistent data. In addition to health insurance eligibility, this function would support verification of registration in programs and registries, such as chronic care case management and immunization registries. A system would likely verify health insurance eligibility prior to the encounter, but would verify registration in case management or immunization registries during the encounter.\nExample:\nA US Realm example could include information about capturing VFC eligibility status as this is a requirement for any provider using federally funded vaccine in the USA.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.9.2-01",
"label" : "AS.9.2#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture patient health plan eligibility information for date(s) of service.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.2#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.9.2-02",
"label" : "AS.9.2#02",
"conformance" : [
"SHALL"
],
"conditionality" : true,
"requirement" : "IF the system does not provide the ability to exchange electronic eligibility information (e.g., health plan coverage dates) with internal and external systems, THEN the system SHALL provide the ability to enter and maintain patient health plan coverage dates.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.2#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.9.2-03",
"label" : "AS.9.2#03",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture general benefit coverage information for patients.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.2#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.9.2-04",
"label" : "AS.9.2#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD store eligibility date(s) of service, coverage dates, general benefits and other benefit coverage documentation for service rendered according to scope of practice, organizational policy, and/or jurisdictional law.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.2#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.9.2-05",
"label" : "AS.9.2#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture electronic eligibility information from internal and external systems.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.2#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.9.2-06",
"label" : "AS.9.2#06",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render information received through electronic prescription eligibility checking.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.2#6"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.9.2-07",
"label" : "AS.9.2#07",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture and maintain patient registration in special programs (e.g., registries and case management).",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.2#7"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.9.2-08",
"label" : "AS.9.2#08",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to analyze eligibility and coverage information for inconsistencies (e.g., coverage dates, patient identity data, coverage status), and render a notification to the user regarding identified inconsistencies.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.3.2#8"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.9.2-09",
"label" : "AS.9.2#09",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render information received through provider eligibility checking."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.